Birmingham City Council
Tree preservation zone
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
THE BIRMINGHAM (LAND REAR OF 71 FEATHERSTONE ROAD, KINGS HEATH) TPO 1975
- reference
- 136
- name
- THE BIRMINGHAM (LAND REAR OF 71 FEATHERSTONE ROAD, KINGS HEATH) TPO 1975
- tree-preservation-order
- TPO 136
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.897424 52.424289,-1.897387 52.424284,-1.897376 52.424281,-1.897364 52.424275,-1.897354 52.424268,-1.897339 52.424254,-1.897332 52.424241,-1.897331 52.424161,-1.897333 52.423802,-1.897409 52.423803,-1.897500 52.423801,-1.897500 52.423797,-1.897543 52.423786,-1.897663 52.423744,-1.897756 52.423716,-1.897885 52.423674,-1.897917 52.423666,-1.897941 52.423645,-1.897947 52.423616,-1.897942 52.423615,-1.897967 52.423564,-1.897973 52.423563,-1.897977 52.423544,-1.897972 52.423524,-1.897976 52.423514,-1.897999 52.423427,-1.898011 52.423373,-1.898023 52.423341,-1.898037 52.423275,-1.898038 52.423264,-1.898043 52.423264,-1.898049 52.423239,-1.898051 52.423236,-1.898009 52.423233,-1.897935 52.423231,-1.897524 52.423229,-1.897479 52.423227,-1.897389 52.423227,-1.897237 52.423204,-1.897012 52.423190,-1.896996 52.423182,-1.896747 52.423159,-1.896737 52.423323,-1.896709 52.423491,-1.896715 52.424206,-1.897193 52.424219,-1.897194 52.424286,-1.897192 52.424371,-1.897424 52.424289)))
- point
- POINT (-1.89724 52.42364)
- notes
- The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
- entry-date
- 2026-07-25
- start-date
- end-date
How to fix this issue
Your data is missing a tree-preservation-order.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Birmingham City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL